Update click, mark mkdocs as not to be upgraded.#204
Update click, mark mkdocs as not to be upgraded.#204freakboy3742 merged 2 commits intobeeware:mainfrom
Conversation
|
This failure is happening on |
|
There are two spots in every translation where the |
freakboy3742
left a comment
There was a problem hiding this comment.
As discussed in person yesterday, there's some rendering issues that seem to be related to translation of code blocks - but those were pre-existing. Landing this as is because it's clearly a fix for other problems (see beeware/beeware.github.io#766).
For posterity: The relevant reference is mkdocs/mkdocs#4077 — and the thread seems like the single maintainer is looking to entirely replace and massively simplify MkDocs while removing its entire plugin system. So I think "not updating" is definitely the right call here; longer-term we should move to Zensical. |
|
FWIW: It's possible to suppress the other warning from Material as well if it's desirable to do so. I'm unsure of where the literate-nav warning is suppressed in the current codebase, so I'm posting the instructoins here: https://squidfunk.github.io/mkdocs-material/blog/2026/02/18/mkdocs-2.0/#what-this-means-for-you — in the blue box is the instructions. We need to set |
|
FTR: The fix is in tox.ini. Look for |
I've opened #211 on this repo; I think we should be disabling this on other repos whenever we make other doc changes, as I don't have the capacity to make a lot of PRs. |
|
I'd actively encourage you to not create PRs - because this is a really good activity for first time contributors, and we're heading into the PyCon US sprints. |
|
@freakboy3742 Thanks. Should I close #211 since it's already done and other contributors can work on it? |
Click has finally posted an update that fixes the issue that was causing MkDocs live serve to fail.
literate-nav now has a warning stating that it's possible that MkDocs 2.0 may, without warning, replace the
pip install mkdocsinstall. It seems unlikely to be a direct replacement for the current version. I have preemptively added a warning about now upgrading MkDocs, should this happen.PR Checklist: